An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

Hi! I’ve just received my seventh rejection for the exact same reason — Guideline 4.3(a) (Spam) — with no real hope of moving forward. I have been developing a free cross-platform VPN app using Flutter since May 12, 2026, continuously adding new features and refining the codebase. Although the iOS version currently boasts the most extensive functionality, it is still insufficient to successfully pass the review process. Before the last submission, I had a review call with an Apple representative who told me the key issue was "code similarity". I spent time improving the Xray VPN core and optimizing traffic routing. Then, after making minor UI tweaks and leaving the description virtually unchanged, I submitted a new version — only to be rejected again. Honestly, I’m at a loss as to what the problem could be. The app features a well-crafted, proprietary codebase and unique functionality that I haven't seen anywhere else, despite extensive research. Recent iterations have added: A modular configuration builder for VLESS/VMess/Trojan/Shadowsocks protocols that flags user errors during key creation, suggests options, and pings the specified address; VPN usage statistics — broken down by hour, data saved, and frequently visited resources (data is collected only with user consent and deleted upon request); Data usage display aligned with the imported subscription. Could the issue stem from the nature of a cross-platform Flutter app built for iOS? Is it possible that the default codebase simply cannot achieve the level of uniqueness Apple demands? I’m starting to lose hope that publishing a Flutter VPN app is even possible. It feels like the App Store simply doesn't approve apps of this type anymore, regardless of their functionality. Please share your experience in resolving issues like this — specifically, how you managed to pass the review after a "Spam 4.3(a)" rejection? Perhaps someone has also submitted a Flutter VPN app based on Xray Core for review? External TestFlight link from the 6th submission: https://testflight.apple.com/join/cp7a1yMC. To have full access to app, paste key on the initial screen: https://kuzya.fit/sub/oyFnd_p3C0q4u0w4

Hello Apple Developer Community, I submitted my PDF app for review on October 5, 2026, and as of October 14, it is still showing “Waiting for Review.” This is the first submission of my app. I have already sent two emails to App Review Support asking for an update, but unfortunately, I have not received any response. I understand that App Review times may vary, but waiting for nine days without any update is concerning, especially for a new app launch. Could anyone from the community share their recent experience with App Review delays? How long did your app stay in “Waiting for Review” recently? Is anyone else experiencing similar delays? Is there any recommended way to contact Apple and get an update on a pending submission? I would really appreciate any advice or suggestions. Thank you.

Hello App Review team, My individual Apple Developer Program membership was terminated on October 4, 2026 under Section 3.2(f), effective immediately. The notice did not state which conduct was considered fraudulent, so I would sincerely appreciate a review or at least an indication of what triggered it. Case ID: 102985280431. Background: I am a solo developer. My app is a free personal finance tracker (no IAP, no external payments, no hidden or remotely-enabled features). It was approved by App Review on October 2 and was live for about two days before the termination. The membership fee was paid with a card in my own name, and all account information is my own. Things I believe may have looked suspicious to an automated system, and my honest explanation: My Apple ID is also a member (Developer role) of my employer's team, and I use the same Mac for both. When I first set up signing on October 1, Xcode auto-selected my employer's team before I pinned my own team. That request failed and nothing was ever distributed under the wrong team. I set up a GitHub Actions CI pipeline to upload TestFlight builds using an App Store Connect API key. During setup on October 1 it failed several times in about an hour, and each successful run created a new Development certificate because the runner did not keep the private key. This is why there was API activity from both Vietnam (my Mac) and US data centers (the CI runner). I now understand this pattern can look abnormal and have stopped it entirely. I have not used any other account, have not manipulated ratings or reviews, and have never asked users to rate the app. I already replied to the termination email and submitted the "Need assistance with accessing your developer account" form on October 4. The App Review Board appeal form redirects me to developer.apple.com/maintenance/, so I am posting here as well, within the 30-day window. I am happy to provide any documentation (ID, payment proof, CI logs) that would help. Thank you for your time.

So it seems there are others experiencing delays with app submissions and I wanted to add my experience so far. I've been waiting 14 days now while the app submitted is "in review". Has anyone actually gotten an app successfully reviewed in the past 1-2 weeks for iOS? We were trying to meet a launch date, but it doesn't seem like this will happen...Apple states that 90% of reviews are completed within 24 hours, this seems to be a far stretch at the moment.

Our app was submitted for review on Oct 8th and still today, Oct 14th is stil under "waiting for review" besides emails and inquiries sent. They normally say 48 hs but they are now 300% delayed on days. If someone knows how to formalize an expediting review, pls let me know. We have launch commited for Oct 22nd with people, $ invested, press, etc... Is very frustrating. Tks for your time ! Rgds, Ignacio.

Hello App Review team, Our iOS app "Pockit: Save & Search Anything" (version 2.0.2, Apple ID 6819025107) was submitted on October 7, 2026 at 10:41 AM IST. It has been in "Waiting for Review" for 7 days. In that time we have received no message, no update and no estimate. We sent a status inquiry through Contact Us on October 12 (Case ID 102993772847). No reply. Apple says most apps are reviewed within 24 hours. We are at 7 days with no explanation. The review process is taking far too long, and the communication about its status is close to none. The app is live on Google Play with real users, and our iPhone users are waiting for it. All agreements are accepted and there are no open issues on our side. We are not asking for special treatment. We are asking for two things: Review the app. Tell us its status. If anything on our side is holding it, tell us what, and we will fix it the same day. Thank you.

Is Anyone Else Experiencing This? I'm curious to know whether other developers are experiencing unusually long App Review delays. My app, TalkCity (version 1.0.3, build 23648159), has been in the review process since October 1. Today is October 13, and 12 days later, all five submitted items remain under review, with no final decision or explanation. Frankly, I find this situation frustrating As an independent developer, I've invested significant time, money, and effort into building this application. Having an entire launch held hostage by an unpredictable review process, with absolutely no transparency, is incredibly frustrating. I fully understand that Apple needs to review applications carefully. But how can developers reasonably plan launches, marketing campaigns, or business operations when reviews can drag on for nearly two weeks without any meaningful communication? We are expected to follow Apple's guidelines to the letter, yet there seems to be very little accountability when it comes to review timelines. I'd genuinely like to hear from other developers: Are you also experiencing unusually long review times recently? Has anyone had an app stuck in review for this long? Did you eventually receive an explanation, or did the review simply move forward without one? Is there anything that actually helped resolve the delay? I believe this deserves a broader discussion. Independent developers shouldn't have to operate in complete uncertainty while their businesses are on hold.

Hi everyone, I submitted my app for App Review on August 14, 2026, at 2:39 PM. I later submitted an updated version again on September 9, 2026. The latest submission has been showing “In Review” for the past 5 days, but I still haven’t received any review decision or additional information from the App Review team. As I understand it, once an app enters the “In Review” status, a review decision is generally provided after the review is completed. However, in my case, the status has remained unchanged for several days. Has anyone experienced a similar situation recently? Is it normal for an app to remain in “In Review” for this long, or is there anything I should do from my side? Any advice or guidance would be appreciated. Thank you!

Hello everyone, I am designing an in-app subscription and pass extension/upgrade system for an iOS app and want to ensure full compliance with App Store Review Guideline 3.1.1. Because pricing in our system depends on the user's historical purchase price rather than static store catalog prices, direct fixed-SKU purchases aren't sufficient on their own. Business Logic Overview Extensions: An extension costs 50% of the price the user originally paid for their plan. Example: If a user bought Plan A at $200, their extension cost is $100 (even if Plan A currently retails at $150). Upgrades: An upgrade charges the delta between the target plan's current price and the user's original purchase price. Example: A user bought Plan A for $200, and Plan B currently costs $250. The upgrade cost is $\max(0, 250 - 200) = 50$. Proposed Technical Solution User requests an extension or upgrade from the iOS client. The backend server calculates the exact delta amount based on user purchase history. The backend maps this calculated amount to a pre-defined Tiered StoreKit Product ID (e.g., com.app.tier_50). The iOS app receives the Product ID and executes the transaction via StoreKit 2 (Product.purchase()). The backend validates the transaction JWS signature with Apple and updates the user's access duration. Questions for the Community & Apple Engineers Has anyone implemented backend-resolved dynamic Tiered SKUs for top-ups or price deltas? Did this pass App Review without issues under Guideline 3.1.1? Are there recommended patterns when configuring price-point tier SKUs (Consumable vs Non-Renewing Subscription) in App Store Connect for variable delta payments? For auto-renewing subscriptions, is it preferred to handle extensions strictly via StoreKit 2 Promotional Offers rather than delta SKUs? Any feedback or real-world experience with similar pricing structures would be greatly appreciated!

Hello App Review Team, After receiving a rejection and responding to the review feedback, I resubmitted Tiebry (iOS, version 0.2.0). It has remained in “Waiting for Review” for nine days. Submission details: Date submitted: October 5, 2026 at 11:42 AM (Brisbane time) Submission ID: ec24cbce-2ac2-49ea-804e-7952e096daf8 Submitted by: Guido Paez Last updated by: Apple Support case: 102989822336 I have only received automated acknowledgements from Developer Support. Could you please check whether anything is blocking the submission or requires action from us, and help move the review forward? Thank you, Guido Paez TIEBRY PTY LTD

Hello everyone, I’m developing a work management app using React Native/Expo for multiple companies. The apps share a common codebase and similar core functionality, but each company has its own app name, logo, bundle ID, and company-specific data. Each company wants a separate app publicly available on the App Store so users can search for and download it. Private distribution through Custom Apps or a single shared app with a company selector would not meet their requirements. I’d like to understand how App Review Guidelines 4.3(a) and 4.2.6 apply to these two scenarios: 1. All apps published under one organization’s developer account Our company would develop and publish all client apps under our own Apple Developer Program organization account. Is there a compliant way to support this model? What requirements would each app need to meet? 2. Each app published under the client company’s own developer account Each client company would enroll in the Apple Developer Program and publish its app under its own organization account, while our team handles development and assists with submission. Could these apps still be rejected under Guideline 4.3(a) because they share a codebase and similar functionality? For both scenarios, I’d appreciate clarification on the following: What differences in functionality, content, or business workflows would help establish each app as a distinct product? How does Guideline 4.2.6 apply to this shared-platform model? What supporting documentation should we provide, such as development contracts or letters of authorization? How should we explain the business need for separate apps in App Review Notes? Has anyone successfully implemented a similar model? I’m looking for a compliant, sustainable approach, rather than a workaround to the review guidelines. Thank you for your advice and experience.

Hello Apple Developer Community, I'm looking for guidance regarding two new iOS app submissions that have both remained in “Waiting for Review” for nearly a week. One of the apps is CosmoLife. We have already requested an expedited review and contacted Apple Developer Support multiple times, but we haven't received a resolution yet. Both submissions are still waiting for review, and we're trying to understand whether this is normal queue time or whether there could be an account-level or submission-related issue. Could anyone share guidance on: Whether simultaneous submissions of two new apps can affect review timelines. How to check the status of a pending expedited review request. The appropriate escalation path when an app remains in “Waiting for Review” for several days. We understand that review timelines can vary and are not asking for any special treatment. We'd appreciate any guidance on the appropriate next steps. Thank you!

Hello Apple Developer Community, I'm looking for guidance regarding two new iOS app submissions that have both remained in “Waiting for Review” for nearly a week. One of the apps is CosmoLife. We have already requested an expedited review and contacted Apple Developer Support multiple times, but we haven't received a resolution yet. Both submissions are still waiting for review, and we're trying to understand whether this is normal queue time or whether there could be an account-level or submission-related issue. Could anyone share guidance on: Whether simultaneous submissions of two new apps can affect review timelines. How to check the status of a pending expedited review request. The appropriate escalation path when an app remains in “Waiting for Review” for several days. We understand that review timelines can vary and are not asking for any special treatment. We'd appreciate any guidance on the appropriate next steps. Thank you!

Hello App Review team, Our two iOS apps from the same team have been in "Waiting for Review" since 6 October 2026 with no change and no new messages: NamuGo (Apple ID 6806743367), version 1.0 (22) NamuGo Master (Apple ID 6806743263), version 1.0 (14) On 1 October both received a Guideline 2.1 Information Needed request. On 6 October we replied in App Store Connect with screen recordings from a physical iPhone and written answers to all six questions, added them to the review notes, and resubmitted. An expedited review was requested and confirmed for both on 11 October, and we contacted Developer Support on 13 and 14 October. The screen recordings are also in the Attachment field of App Review Information. Our developer account was converted from individual to organization on the same day we resubmitted. All agreements, tax, banking, DSA and DAC7 information are active. Could you please check whether anything is holding these submissions or whether we need to do anything? Thank you.

Hello, We're preparing guidance about iPhone Duo for our team and clients. Could someone confirm whether the following understanding is correct? Starting April 2027, apps uploaded to App Store Connect must be built with the iOS 27 SDK or later. Apps built with the iOS 27 SDK are resized on iPhone Duo, and there's no way to keep the compatibility presentation (the app shown at its previous size in the center of the inner display). So any app update submitted after April 2027 will be resized on iPhone Duo. Starting April 2027, apps using the iOS 27.1 SDK or later must include iPhone Duo screenshots. Under the guidance for Guideline 2.3.3, the majority of screenshots for each device must show the app in use on that device, and screenshots must not misrepresent the app's actual interface. So iPhone Duo screenshots need to be captured from the app actually running on iPhone Duo or the iPhone Duo simulator, not mocked up or resized from other iPhone screenshots. If App Review finds that an app's UI is broken on iPhone Duo and can't be operated (for example, buttons can't be tapped), the app may be rejected under Guideline 2.1(a), in the same way iPhone-only apps have been rejected for issues found on iPad. If any part is inaccurate, we'd appreciate a correction. References: https://developer.apple.com/iphone-duo/prepare/ https://developer.apple.com/forums/thread/847836 https://developer.apple.com/help/app-store-connect/reference/app-information/screenshot-specifications https://developer.apple.com/help/app-review/guideline-reference/2-3-3-screenshots Thank you.

Hello Apple Developer Community, The version of our app currently available on the App Store contains a serious bug that affects users’ ability to use the app normally. On October 8, 2026, we submitted a new version that fixes this issue and requested an expedited review. As of October 14, 2026, approximately four days later, the submission is still waiting for review and the review process has not started. We have also followed up by email. Unfortunately, our existing users continue to experience the problem while we are unable to make the fix available to them. We understand that the App Review team handles many submissions. Given the ongoing impact on our users, could someone advise on the appropriate way to check the status of our expedited review request or follow up on this urgent bug-fix submission? We can provide the app and submission details through a private support channel if needed. App name: Jewel Muse! App ID: 6785241915 App Store link: https://apps.apple.com/app/id6785241915 Thank you for your time and assistance. Jewel Muse! Team

Hi all. Looking for any guidance from Apple folks who watch this board. I have two apps on a new developer account that have sat in "Waiting for Review" for ten days: Headed Back 0.1.0 (app 6818855256), submitted Oct 3 at 8:40 PM ET Headed In 0.3.0 (app 6817955207), submitted Oct 3 at 4:24 PM ET Headed Back got a Guideline 2.1 Information Needed request on Oct 3. I answered every question the same evening, attached the requested iPhone screen recording to the version's App Review Information, and resubmitted. Nothing has moved since. An expedited review request was approved on Oct 9. Three smaller study apps on the same account have been waiting since Oct 9 (also after answering a 2.1 questionnaire). I opened a status request with Developer Support on Oct 12 (case 102991644523) and have the auto-reply only. Phone support points back to the web form. Is there anything else I should be doing here, or is this a normal wait after a 2.1 questionnaire on a new account? I am happy to supply anything App Review needs. Thanks.

Our first iOS app submission (Apple ID 6782193284, version 1.0) was submitted on October 2 and still shows “Waiting for Review.” No reviewer messages have arrived in App Store Connect, and agreements, tax, and banking are active. We sent a support request on October 8 and have only received the automatic reply. Could App Review confirm that the submission is in the queue and tell us if anything is needed from us? Thank you.

I'm writing this post to express my serious frustration and disappointment with Apple's App Review process. We submitted our app, Virtual Pro Association, on September 28, 2026. Today is October 13, and after 15 days, our app is still not approved. Here is the timeline: September 28: Initial submission. October 6: Apple finally started reviewing our app after approximately 8 days. October 6: The app was rejected. We fixed the reported issues and resubmitted it within approximately one hour. October 13: Seven more days have passed, and our app is still stuck in "Waiting for Review." We even requested an expedited review, which Apple accepted. Apple explicitly stated that if our submission was rejected, the corrected version would automatically return to the expedited review queue. So what exactly does "expedited" mean if we are still waiting after all this time? We have contacted Apple Developer Support multiple times, but all we receive are generic responses telling us to wait, without any meaningful explanation or estimated timeline. This is not acceptable. Behind every application, there are real people working hard. Developers, designers, administrators, and entire teams invest countless hours building, testing, and preparing their products for launch. We have responsibilities, deadlines, communities waiting for our services, and projects that depend on these releases. Apple cannot simply leave developers waiting indefinitely without transparency or accountability. We pay an annual fee to participate in the Apple Developer Program. We understand that app reviews are necessary for security and quality, and we fully support that process. But paying developers should reasonably expect an efficient review service, clear communication, and predictable procedures. If Apple's App Review team cannot handle the current volume of submissions, Apple should invest in hiring more reviewers and improving its review infrastructure. Developers should not have to repeatedly contact support, request expedited reviews, and post on forums just to find out why their applications are sitting in a queue for weeks. We are not asking Apple to approve applications without reviewing them. We are asking Apple to review them within a reasonable timeframe. Our app has been tested extensively, the reported issues were corrected immediately, and we have done everything requested of us. Yet we are still waiting. 15 days. An approved expedited review request. A corrected submission. No meaningful progress. Apple, developers deserve better. We need transparency, accountability, and a review process that respects the time and work of the people who build applications for your ecosystem. How many other developers are experiencing the same situation right now?